Skip to content

Conversation

@austinlparker
Copy link
Member

@austinlparker austinlparker commented Oct 23, 2025

Adds a blog from the GC discussing proposed changes to stability and future project work/direction. cc @open-telemetry/governance-committee


Preview: https://deploy-preview-8208--opentelemetry.netlify.app/blog/2025/stability-proposal-announcement/

@austinlparker austinlparker requested a review from a team as a code owner October 23, 2025 16:45
@otelbot-docs otelbot-docs bot requested a review from a team October 23, 2025 16:45
@github-actions github-actions bot added the docs:blog An issue requesting a blog post, or a PR for a new blog post label Oct 23, 2025
@julianocosta89
Copy link
Member

One point that is not mentioned on the blog, but it is important to help users navigate the project is repositories structure.
I was discussing SemConv with a colleague and I've noticed that each programming language has a different way of organizing them:

It would be great if we could follow the same pattern across all languages.

@dmathieu
Copy link
Member

I wonder if this post should emphasize more that all these are proposals that (I think and hope) need to be properly discussed with maintainers and contributors before they are finalized, and that the way they end up being implemented may change based on discussions with all the stakeholders of the project.

Copy link
Member

@pichlermarc pichlermarc left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Big change. Personally, I love this idea. 🙌

I think this aligns very well with the the idea behind the JS SIG's focus-topic selection criteria - having backing for something like this on a project-wide level AND having this communicated so publicly sounds like it has the potential to be a huge boost to stabilization efforts.

Copy link
Contributor

@evan-bradley evan-bradley left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Mostly just wordsmithing suggestions right now, thanks for putting this together!

@austinlparker
Copy link
Member Author

notes from gc call

  • add an exec summary to top
  • expand on next steps (don't overcorrect or overread into this blog -- we will figure out the guidance thru the process)
  • add alternate feedback avenues outside of GitHub discussion (listserv, end user sig, slack, office hours)
  • set timeline expectations; define order of operations and rough time box for it

austinlparker and others added 10 commits November 7, 2025 13:09
- Add 'and lack of stability' to complexity statement
- Change 'own your own instrumentation' to 'publish and maintain your own instrumentation'
- Remove 'not as well-defined as the earlier proposals' language
- Clarify that epoch releases don't require changing component versioning/release cadence
- Change "Our Goals" from emphasis to heading (MD036)
- Rename duplicate "Background" headings to be unique (MD024)
- Rename duplicate "Goals and Objectives" headings to be unique (MD024)
Add deprioritize, incentivized, and rollouts to dictionary.
Move spelling exceptions from global dictionary to page-local
to avoid affecting other files.
@chalin chalin force-pushed the ap/addStabProjAnnounceBlog branch from 8295e6f to 5be7064 Compare November 7, 2025 18:09
Copy link
Member

@mtwo mtwo left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@austinlparker the new intro resolves my concerns, thanks for doing all of the legwork on this - I know that it wasn't easy

Copy link
Member

@alolita alolita left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks @austinlparker for patiently looking at the feedback on this post and incorporating :-) This post reads well #ShipIt

Copy link
Member

@tiffany76 tiffany76 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

A few tiny fixes, but otherwise good to go. 🚀

Copy link
Contributor

@chalin chalin left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

See inline comments, they suggest changing to today's date, and other front-matter cleanup.

Otherwise I defer to others for a full review.

@otelbot-docs otelbot-docs bot requested a review from a team November 8, 2025 02:04
Co-authored-by: Patrice Chalin <[email protected]>
Co-authored-by: Tiffany Hrabusa <[email protected]>
@austinlparker austinlparker added this pull request to the merge queue Nov 8, 2025
Merged via the queue into open-telemetry:main with commit e5d8ad0 Nov 8, 2025
22 checks passed
@austinlparker austinlparker deleted the ap/addStabProjAnnounceBlog branch November 8, 2025 02:14
@svrnm
Copy link
Member

svrnm commented Nov 8, 2025

🙌

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

docs:blog An issue requesting a blog post, or a PR for a new blog post

Projects

Status: Done

Development

Successfully merging this pull request may close these issues.